Skip to content

Conversation

@labkey-tchad
Copy link
Member

Rationale

The test-side name validation should focus on validating the random portion of generated names. It should assume that the test has provided a valid base name.

Related Pull Requests

Changes

  • Make name validity check focus on the random portion
  • Create RandomName record for randomly generated names

@labkey-tchad
Copy link
Member Author


public static boolean isNameInvalidLocal(DomainKind domainKind, @Nullable String domainName, @Nullable String fieldName)
private static final Pattern COLON_NAME_PATTERN = Pattern.compile(":[a-zA-Z]{3}"); // Avoid illegal patterns like ":Date"
private static boolean isNameInvalidLocal(DomainKind domainKind, @Nullable RandomName domainName, @Nullable RandomName fieldName)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nit:
I realize this is not a new method, but in Java, when naming methods that return a boolean value to indicate validity, the convention generally favors positive phrasing. isNameValid vs. isNameInvalid

@labkey-tchad labkey-tchad merged commit 27a42c5 into release25.9-SNAPSHOT Sep 11, 2025
6 of 7 checks passed
@labkey-tchad labkey-tchad deleted the 25.9_fb_fixRandomPlateName branch September 11, 2025 19:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants